Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[modbus.lambda] Lambda Heat Pump #18248

Open
wants to merge 305 commits into
base: main
Choose a base branch
from

Conversation

chilobo
Copy link

@chilobo chilobo commented Feb 10, 2025

Based on the Stiebel Eltron bundle by Paul Frank I contribute a bundle to manage Lambda Heat Pumps as a OSG addon to the Modbus Binding.

I did some testing by adding my jar to the local addon directory.
@agio tested it with two instances of heating circuits - thank you!
@lsiepel helped a lot by reviewing and suggesting changes which resulted in a #17595
@david-pace helped to point me to work with a separate branch - see #17846

See the README.md for restrictions on usage.

The binding is based on the Modbus description of the manufacturer:
(https://lambda-wp.at/wp-content/uploads/2024/11/Modbus-Protokoll-und-Beschreibung.pdf)
A few parts of the description are not implemented. If you feel you need them, just open a request.

Compressed directory:
org.openhab.binding.modbus.lambda.zip

@chilobo chilobo requested a review from a team as a code owner February 10, 2025 09:54
jlaur added 28 commits February 10, 2025 10:58
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Christian Koch <[email protected]>
@chilobo
Copy link
Author

chilobo commented Feb 10, 2025

Oops - I got a message that my commits were not signed off properly, so I followed the advice:

git rebase HEAD~16 --signoff
git push --force-with-lease origin modbus-lambda-binding

... which caused the addition of too many reviewers. I am sorry for that - what do I do now?

@david-pace
Copy link
Member

First of all, I noticed that you created a merge commit (Merge branch 'openhab:main' into main). As a general rule, this should be avoided (refer for this community thread for some background information) as it mostly messes up your git history.

As it looks currently this also happened to your git history. Your commits are not in a "chain" anymore but are completely mixed up with the other commits. The state you want to achieve looks like the following:

grafik
  • your local main and origin/main should be in sync and point to a fairly recent commit from the official openHAB repository
  • your commits should be a "chain" of commits on top of the main commit (could also be just 1 commit)
  • you should have a dedicated branch for your PR that points to the last commit in your chain

In your case the only solution I can think of is to start again:

  1. Backup your work. I think you are developing a new binding, so it should be fairly easy by just copying the whole binding folder you created to a safe place.
  2. Go to the github page of your fork and click sync fork -> update branch. The main branch of your fork should now be in sync with the official openhab addons branch. I don't know which options you have there since your main branch seems to be messed up, too. You basically want to throw away everything you did on your main branch and reset to the state of the original openhab:main branch. When in doubt, you can post a screenshot of what options you have there.
  3. Go back to your IDE and switch back to the main branch
  4. Pull the main branch
  5. In case your main branch is now not in sync with the commit shown in step 1, find the commit and perform a git reset --hard on that commit. Your main branch should now be in sync with the commit from step 1.
  6. Force-push your main branch. Now your main branch should be in a good state again.
  7. Now you can either switch to your modbus-lambda-binding branch and perform a git reset --hard on the latest main commit, or you can delete the branch and create it again starting from the latest main commit. The branches main and modbus-lambda-binding should now point to the very same commit.
  8. Switch to your modbus-lambda-binding branch
  9. Restore the binding backup from step 1
  10. Create a new commit containing all the changes for your binding (don't forget to sign it off)
  11. Force-push your modbus-lambda-binding branch
  12. Create a new pull request if possible

I hope this helps. If any of the others have a better idea, please let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.